Name
|
Description
|
| PegaRules:AutoTest
|
Allows access to use Automated Unit Testing. |
| PegaRULES:Batch
|
For background requestors, including agents. |
| PegaRULES:Guest
|
Allows unauthenticated access with minimal access. |
| PegaRULES:Guest-Maximum
|
Allows unauthenticated access with more capabilities, including the ability to open and update work items assigned to self. |
| PegaRULES:PegaAPI
|
Allows a user to use the Pega API. |
| PegaRULES:SysAdm4
|
Allows a developer to have full capabilities. |
| PegaRULES:User1
|
Application user with limited capabilities. Cannot perform assignments on worklists other than user's own worklist. Uses the Get Most Urgent to obtain the assignments to work on next. |
| PegaRULES:User4
|
For users with broader capabilities. Can open any work object in the application. Can perform assignments only on own worklists. |
| PegaRULES:WorkMgr4
|
Allows a work manager to have full capabilities, and can view and update delegated rules. |
| PegaRULES:SysArch4
|
For a business analyst or a system architect who defines processes, classes, and properties (Data Model category), and can develop activities. |
| PegaRULES:ProArch4
|
For a process architect who focuses on flows and other rules in the Process and User Interface categories. |
| PegaRULES:EditorCollaborator
|
For collaborators who participate in development of the application as editors. Can view and change application assets. |
| PegaRULES:ViewerCollaborator
|
For collaborators who participate in development of the application as reviewers. Can view application assets, but cannot change them. |